@TomerHeber generally looks good to me. But I am not familiar with tfschema so I am not sure what the - actually means. It is something supported by it? Or it is "customer syntax" you have added? Because I see that on the read/write methods it needs a spacial reference.

Maybe can you explain more about it and the goal here?

@razbensimon I also added an explanation to DEVELOPMENT.md.

The writeResourceData (and readReasourceData) is a utility function that reads (writes) all the fields in (to) the interface and updates (reads) the schema via set (get) calls.
This is future proof: in case you add more fields to the schema/api - no additional coding is needed (other than updating the schema).

In general, if a struct field is called "EnvironmentId" it will be called in the schema "environment_id".
tfschema is a tag (created by us) used by writeResourceData and readReasourceData, to override this behavior. (such as overriding the default CamalCase to snake_case conversion). E.g. convert "EnvironmentId" to "my_special_environment_id".

Just as json:"-" omits fields. I added the same option to tfschema. Some fields we may still want to handle manually and avoid using writeResourceData and readResourceData.